Enter recipe and energy hatch. Computes regular + laser overclocks, per-slice power, pipelined throughput — exactly as OverclockCalculator with laser OC does in GT5-Unofficial (GTNH 2.8.4).
Outputs per minute for this recipe, sweeping total hatch amps (log scale). Marker = your current setting.
EU consumed per output, as a multiple of the base recipe EU. Laser overclocks (×4.3, ×4.6, …) make each halving progressively more expensive.
How the AAL computes this: per-slice budget is hatchV × amps ÷ slices, per-slice base time is duration ÷ slices. Regular overclocks (×4 power, ×2 speed) run while 4× power fits the budget, capped at hatchTier − recipeTier. Laser overclocks then continue past the tier cap using amperage alone, costing ×4.3, ×4.6, ×4.9… per step (penalty 0.3, configurable), each still halving time, until the budget is hit or slice time reaches 1 tick — the AAL never overclocks below 1 tick per slice. Parallels: the AAL always runs 1 true parallel; with batch mode on (sneak + wire cutter), it starts P = min(⌊128 ÷ OC'd slice time⌋, available input sets ÷ slices, 128) recipes per pass — outputs ×P and slice time ×P together, so throughput is unchanged; it's an item-logistics saver. Pattern each recipe input (items and fluids) ×P into the busses/hatches, and stock the first input hatch with at least P × slices fluid sets or batching degrades. Real throughput gain is pipelining — slice 0 accepts a new recipe every slice-time, so steady-state rate is one output per slice-time, not per full recipe.